Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae69884c35f086693af126879da8c7c45392fa0d279d3bfc47ca5f0e3fe2b79c

Tx prefix hash: 65354acf1b465628af376d22906e4f7a0d362aee6540f10189eac3467df4961f
Tx public key: 39655c887fdc9a7fad3f3616b6517fd0d470724493b8074529e1b75d8ab86328
Timestamp: 1722819190 Timestamp [UCT]: 2024-08-05 00:53:10 Age [y:d:h:m:s]: 00:159:05:21:09
Block: 1080921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113926 RingCT/type: yes/0
Extra: 0139655c887fdc9a7fad3f3616b6517fd0d470724493b8074529e1b75d8ab8632802110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c15697786ffb6f9b1b96bb78919e4b0481977d2933b9a0d417299467c0b7acf 0.600000000000 1554468 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": 1080931, "vin": [ { "gen": { "height": 1080921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c15697786ffb6f9b1b96bb78919e4b0481977d2933b9a0d417299467c0b7acf" } } ], "extra": [ 1, 57, 101, 92, 136, 127, 220, 154, 127, 173, 63, 54, 22, 182, 81, 127, 208, 212, 112, 114, 68, 147, 184, 7, 69, 41, 225, 183, 93, 138, 184, 99, 40, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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