Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d19d8e7a218a31a63c65f27f65e0b450a65c0408c2f2018d6307a4e90aaf2ad

Tx prefix hash: f023aee5532e7964ca53f2bb8614902f1721732ab95705b45be235c80edec888
Tx public key: ded19e2d21ff45d75b96afa6bbaf9403a4f07b6d57a08e8f7b3e9798abee1e5e
Timestamp: 1724901722 Timestamp [UCT]: 2024-08-29 03:22:02 Age [y:d:h:m:s]: 00:087:12:32:40
Block: 1098188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62608 RingCT/type: yes/0
Extra: 01ded19e2d21ff45d75b96afa6bbaf9403a4f07b6d57a08e8f7b3e9798abee1e5e02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be1f4ef2af3839bfffa4a0f8669e9842b6d263c849c3396b47f411a1976dbaa1 0.600000000000 1573819 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": 1098198, "vin": [ { "gen": { "height": 1098188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be1f4ef2af3839bfffa4a0f8669e9842b6d263c849c3396b47f411a1976dbaa1" } } ], "extra": [ 1, 222, 209, 158, 45, 33, 255, 69, 215, 91, 150, 175, 166, 187, 175, 148, 3, 164, 240, 123, 109, 87, 160, 142, 143, 123, 62, 151, 152, 171, 238, 30, 94, 2, 17, 0, 0, 0, 4, 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