Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39a710f9c8ab5017b8dea708f9b8cb7ddc0c76c7d1512060e1159dc63ec227a2

Tx prefix hash: b1f6749cab39912023b26894ff209d639e51153749f8d157dcd2ecfeaffda869
Tx public key: 65c699e0d059df66ae9ddf0596260955971e1a3df9cb324247ee4a627ca16bdb
Timestamp: 1718763808 Timestamp [UCT]: 2024-06-19 02:23:28 Age [y:d:h:m:s]: 00:286:22:55:14
Block: 1047308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205042 RingCT/type: yes/0
Extra: 0165c699e0d059df66ae9ddf0596260955971e1a3df9cb324247ee4a627ca16bdb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 447fa10f2d6d09e365ac498317c794f5ccdd426c4123bf3ad444896469527e59 0.600000000000 1517127 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": 1047318, "vin": [ { "gen": { "height": 1047308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "447fa10f2d6d09e365ac498317c794f5ccdd426c4123bf3ad444896469527e59" } } ], "extra": [ 1, 101, 198, 153, 224, 208, 89, 223, 102, 174, 157, 223, 5, 150, 38, 9, 85, 151, 30, 26, 61, 249, 203, 50, 66, 71, 238, 74, 98, 124, 161, 107, 219, 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