Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2a13f8de9e606a4e4cdaeb59b74306aea9898f96371a708981494911ce1a8b57

Tx prefix hash: cee4930cbf1758bbb3954ea22a6a83dbf4038f8f19626f35db2f6d86c63159c3
Tx public key: 0caa179d5d5826c4bfb6a66141e2cc8972041c4d9dbfc82b52321830fcf8eed6
Timestamp: 1717682092 Timestamp [UCT]: 2024-06-06 13:54:52 Age [y:d:h:m:s]: 00:302:06:58:31
Block: 1038347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216022 RingCT/type: yes/0
Extra: 010caa179d5d5826c4bfb6a66141e2cc8972041c4d9dbfc82b52321830fcf8eed60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baab6e7ba7b69bd0cc989d3c6830e7bfd35b374d68ebd2ee84290962e37d4fae 0.600000000000 1506908 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1038357, "vin": [ { "gen": { "height": 1038347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baab6e7ba7b69bd0cc989d3c6830e7bfd35b374d68ebd2ee84290962e37d4fae" } } ], "extra": [ 1, 12, 170, 23, 157, 93, 88, 38, 196, 191, 182, 166, 97, 65, 226, 204, 137, 114, 4, 28, 77, 157, 191, 200, 43, 82, 50, 24, 48, 252, 248, 238, 214, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8