Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f357aaf3694ec85fcbb875511caadc30e30548df66a8ec360c5f3a25da894853

Tx prefix hash: 634ab60a188ed14e0b95322df203a02eb16d409537bb1237317ebe34f3271308
Tx public key: d2ae9576e9b341cb452c3a5d60d57ef6985d2b408cbcbfb9f9382a34f1529106
Timestamp: 1720744051 Timestamp [UCT]: 2024-07-12 00:27:31 Age [y:d:h:m:s]: 00:270:06:02:20
Block: 1063731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193063 RingCT/type: yes/0
Extra: 01d2ae9576e9b341cb452c3a5d60d57ef6985d2b408cbcbfb9f9382a34f152910602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aed872fd34302dee58df5c5a2840192575c1f8616e400a34990d6d8b66fe0ef 0.600000000000 1534248 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": 1063741, "vin": [ { "gen": { "height": 1063731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aed872fd34302dee58df5c5a2840192575c1f8616e400a34990d6d8b66fe0ef" } } ], "extra": [ 1, 210, 174, 149, 118, 233, 179, 65, 203, 69, 44, 58, 93, 96, 213, 126, 246, 152, 93, 43, 64, 140, 188, 191, 185, 249, 56, 42, 52, 241, 82, 145, 6, 2, 17, 0, 0, 0, 9, 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