Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57358fe2cf5d74c073b234598d6420bcf508ff21e0259d7a3a24c02b998bc390

Tx prefix hash: 387470c372c6bb2b42ec3e2bd29da0cb7f36f9ec5af22a475f3902fada6504ef
Tx public key: fe2030d8e8eaa6df006ab7b3e12c9639e0034b49f533152c06701c0a0985caf4
Timestamp: 1720778069 Timestamp [UCT]: 2024-07-12 09:54:29 Age [y:d:h:m:s]: 00:267:09:49:25
Block: 1064015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191040 RingCT/type: yes/0
Extra: 01fe2030d8e8eaa6df006ab7b3e12c9639e0034b49f533152c06701c0a0985caf402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5def99a7723d7709f72faad97a288943efd98394b0ff821fb81881ea28d5cf0e 0.600000000000 1534536 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": 1064025, "vin": [ { "gen": { "height": 1064015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5def99a7723d7709f72faad97a288943efd98394b0ff821fb81881ea28d5cf0e" } } ], "extra": [ 1, 254, 32, 48, 216, 232, 234, 166, 223, 0, 106, 183, 179, 225, 44, 150, 57, 224, 3, 75, 73, 245, 51, 21, 44, 6, 112, 28, 10, 9, 133, 202, 244, 2, 17, 0, 0, 0, 3, 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