Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba904df3ba08c45a84aecd0b6a8c50b9faa4c94d7135538033da87c2924bed1

Tx prefix hash: dd5996d9f151f47a238081748371e05f9b0362af468dbd75781e9297d31b62b7
Tx public key: ec768dcf554b0333fdcb6c31403b09a19c8929ddc33c604cc2746ecb130fe4d9
Timestamp: 1713339459 Timestamp [UCT]: 2024-04-17 07:37:39 Age [y:d:h:m:s]: 00:356:13:52:51
Block: 1002331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254918 RingCT/type: yes/0
Extra: 01ec768dcf554b0333fdcb6c31403b09a19c8929ddc33c604cc2746ecb130fe4d90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f360e193b5b4dd0a7d3b4c610870c85216ffb31fd0fc41d16fd6446ff2013c0d 0.600000000000 1462847 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": 1002341, "vin": [ { "gen": { "height": 1002331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f360e193b5b4dd0a7d3b4c610870c85216ffb31fd0fc41d16fd6446ff2013c0d" } } ], "extra": [ 1, 236, 118, 141, 207, 85, 75, 3, 51, 253, 203, 108, 49, 64, 59, 9, 161, 156, 137, 41, 221, 195, 60, 96, 76, 194, 116, 110, 203, 19, 15, 228, 217, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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