Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45389517a87083a1c411537ff347142ea5f004e208569e10c23bb65b053078f9

Tx prefix hash: 6112ab2e0b7858e2cbbf594638887bb241da65837953fd7916e4b634086641e7
Tx public key: 752461e7d50ef7fa1dbe402bf7e9ed642cfe025ea690ef7a89d0b2c140ac0d5e
Timestamp: 1710509528 Timestamp [UCT]: 2024-03-15 13:32:08 Age [y:d:h:m:s]: 01:084:10:20:28
Block: 978896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321353 RingCT/type: yes/0
Extra: 01752461e7d50ef7fa1dbe402bf7e9ed642cfe025ea690ef7a89d0b2c140ac0d5e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98d38f90273a43e6afe75185aa01f82be274f59eac9854aa0ae7ee8e0e1336b 0.600000000000 1438925 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": 978906, "vin": [ { "gen": { "height": 978896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98d38f90273a43e6afe75185aa01f82be274f59eac9854aa0ae7ee8e0e1336b" } } ], "extra": [ 1, 117, 36, 97, 231, 213, 14, 247, 250, 29, 190, 64, 43, 247, 233, 237, 100, 44, 254, 2, 94, 166, 144, 239, 122, 137, 208, 178, 193, 64, 172, 13, 94, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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