Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb729674175649c4ec69379f5993d3b58c0ff8eab512d221f31a789b41a25abe

Tx prefix hash: 578b64fffa766d54f38fbc1e8d6e0827ac6111f8fdcd71c31a7d4a42d164db16
Tx public key: 5cbdf3c4f177e970c2282fba82c4d2dd8b634013c2be7dd0e9b803a3b6402f16
Timestamp: 1706201252 Timestamp [UCT]: 2024-01-25 16:47:32 Age [y:d:h:m:s]: 01:291:09:38:16
Block: 943129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467083 RingCT/type: yes/0
Extra: 015cbdf3c4f177e970c2282fba82c4d2dd8b634013c2be7dd0e9b803a3b6402f1602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a84f0ed0d2d06d4f62263e0eb1f7fd5f2b912067f6a4408f2c88b62970efb590 0.600000000000 1401329 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": 943139, "vin": [ { "gen": { "height": 943129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a84f0ed0d2d06d4f62263e0eb1f7fd5f2b912067f6a4408f2c88b62970efb590" } } ], "extra": [ 1, 92, 189, 243, 196, 241, 119, 233, 112, 194, 40, 47, 186, 130, 196, 210, 221, 139, 99, 64, 19, 194, 190, 125, 208, 233, 184, 3, 163, 182, 64, 47, 22, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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