Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0976974b7343ada1b512e450720a9eb32b7c7a897ac518f64e6806cc7f7a49ec

Tx prefix hash: fd4e594db2ef695f678b3f71f74267521911dddb60b5f0cd08140170d54b5a2e
Tx public key: 564ce36ecdff354fee0f3f2dcf25f8344198cf0041fd6ffe211579183964c6bb
Timestamp: 1698658573 Timestamp [UCT]: 2023-10-30 09:36:13 Age [y:d:h:m:s]: 01:120:02:20:14
Block: 880837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346797 RingCT/type: yes/0
Extra: 01564ce36ecdff354fee0f3f2dcf25f8344198cf0041fd6ffe211579183964c6bb021100000004faf35c9c000000000000000000

1 output(s) for total of 0.740323231000 dcy

stealth address amount amount idx
00: 09844026115aef721dd337d1663d2c07bc422e1c146414a92a430ecb2f7ae92e 0.740323231000 1336407 of 0

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": 880847, "vin": [ { "gen": { "height": 880837 } } ], "vout": [ { "amount": 740323231, "target": { "key": "09844026115aef721dd337d1663d2c07bc422e1c146414a92a430ecb2f7ae92e" } } ], "extra": [ 1, 86, 76, 227, 110, 205, 255, 53, 79, 238, 15, 63, 45, 207, 37, 248, 52, 65, 152, 207, 0, 65, 253, 111, 254, 33, 21, 121, 24, 57, 100, 198, 187, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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