Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe8511fb24cf46b634925449c1d7dcc50907dcd89e46f9387acae159a91ee975

Tx prefix hash: a402e78dee63976b7d3461984478e9b38fbb96258a97f3396aebb11fedd94a5e
Tx public key: a1fde1f547ffd86f2f8a3e6a3e15288a87617828527b7970675ccc21c29e2c4a
Timestamp: 1734538403 Timestamp [UCT]: 2024-12-18 16:13:23 Age [y:d:h:m:s]: 00:090:18:45:05
Block: 1178001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64659 RingCT/type: yes/0
Extra: 01a1fde1f547ffd86f2f8a3e6a3e15288a87617828527b7970675ccc21c29e2c4a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a74c898cb122012b2d5d42def26fc3bdb7c35734c1ba33ce1e2965dbeeb1f97e 0.600000000000 1664384 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": 1178011, "vin": [ { "gen": { "height": 1178001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a74c898cb122012b2d5d42def26fc3bdb7c35734c1ba33ce1e2965dbeeb1f97e" } } ], "extra": [ 1, 161, 253, 225, 245, 71, 255, 216, 111, 47, 138, 62, 106, 62, 21, 40, 138, 135, 97, 120, 40, 82, 123, 121, 112, 103, 92, 204, 33, 194, 158, 44, 74, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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