Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5810798fd719b429c780d15bfd5dfddcbd7fc29602441180b77eb3d346572489

Tx prefix hash: 78554c4f27bca90fa7e684e494e6814f8bba69a974fdfcf232e29af45e04f1fa
Tx public key: 74814f06a4c922e773be4e62c4a61968e4437727d50c203a624816bbfa50e26f
Timestamp: 1720361111 Timestamp [UCT]: 2024-07-07 14:05:11 Age [y:d:h:m:s]: 00:298:16:00:43
Block: 1060543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213416 RingCT/type: yes/0
Extra: 0174814f06a4c922e773be4e62c4a61968e4437727d50c203a624816bbfa50e26f0211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 651d0891c97d18b14c8a75c129f177c0ffb8840cfcc02b8d76d0b7a9e42a674d 0.600000000000 1531026 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": 1060553, "vin": [ { "gen": { "height": 1060543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651d0891c97d18b14c8a75c129f177c0ffb8840cfcc02b8d76d0b7a9e42a674d" } } ], "extra": [ 1, 116, 129, 79, 6, 164, 201, 34, 231, 115, 190, 78, 98, 196, 166, 25, 104, 228, 67, 119, 39, 213, 12, 32, 58, 98, 72, 22, 187, 250, 80, 226, 111, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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