Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59fb2717e2bf893b2bd79cd82509ca9d3f78e12fd1d4baf2c3f07400384f51da

Tx prefix hash: b022415b67f4971bd3d6115899fc6668786176d0c1b3d19a8db7e84b65a49c77
Tx public key: cbd760ae0af27e8ec1241f68d9d03c0b1ffe5ef864fc34ef0b86fa62724b2078
Timestamp: 1725145014 Timestamp [UCT]: 2024-08-31 22:56:54 Age [y:d:h:m:s]: 00:085:02:54:15
Block: 1100209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60869 RingCT/type: yes/0
Extra: 01cbd760ae0af27e8ec1241f68d9d03c0b1ffe5ef864fc34ef0b86fa62724b207802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aada93d6f4ecebe1c6e14e1a43c2dba017e8e477860a3971fd11575db6e1ff4 0.600000000000 1576182 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": 1100219, "vin": [ { "gen": { "height": 1100209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aada93d6f4ecebe1c6e14e1a43c2dba017e8e477860a3971fd11575db6e1ff4" } } ], "extra": [ 1, 203, 215, 96, 174, 10, 242, 126, 142, 193, 36, 31, 104, 217, 208, 60, 11, 31, 254, 94, 248, 100, 252, 52, 239, 11, 134, 250, 98, 114, 75, 32, 120, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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