Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9d8ed4a0701da0343319cab58c554c4512bfe06080ee90841fc5a3855c7b729

Tx prefix hash: ec09cda60c29751f1730358d6dce7c8064261e2aca90374ff22a60761b2b1804
Tx public key: aeb70a00aded5b646e7b18dbe7a4d40bda21dbcffec472a511b84b2c7f7041f0
Timestamp: 1712770386 Timestamp [UCT]: 2024-04-10 17:33:06 Age [y:d:h:m:s]: 00:342:00:27:32
Block: 997595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244550 RingCT/type: yes/0
Extra: 01aeb70a00aded5b646e7b18dbe7a4d40bda21dbcffec472a511b84b2c7f7041f00211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf903c4552f2ce71e4c3ea5df5712ac442f3e6bc714cf038beab64b40433dcbe 0.600000000000 1458029 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": 997605, "vin": [ { "gen": { "height": 997595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf903c4552f2ce71e4c3ea5df5712ac442f3e6bc714cf038beab64b40433dcbe" } } ], "extra": [ 1, 174, 183, 10, 0, 173, 237, 91, 100, 110, 123, 24, 219, 231, 164, 212, 11, 218, 33, 219, 207, 254, 196, 114, 165, 17, 184, 75, 44, 127, 112, 65, 240, 2, 17, 0, 0, 0, 5, 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