Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f55c267053a9cf06f5661de77930a037d946a3dcb62cf21e14680c8b17616bf

Tx prefix hash: 7ec7d80e92e19f89af72362efeb2099e6a9028f0dbbf1f88d78d80b47b61beb0
Tx public key: 8e74474e76dac46fe264b40a6a59d0aed7c8583bedcfc5c04d9a28467422767c
Timestamp: 1719762370 Timestamp [UCT]: 2024-06-30 15:46:10 Age [y:d:h:m:s]: 00:349:15:03:06
Block: 1055571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249794 RingCT/type: yes/0
Extra: 018e74474e76dac46fe264b40a6a59d0aed7c8583bedcfc5c04d9a28467422767c021100000002ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c73244f21bdaaee18f9892a1a301c12cf0fc05057de6613d000f911c6be32b9 0.600000000000 1525976 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": 1055581, "vin": [ { "gen": { "height": 1055571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c73244f21bdaaee18f9892a1a301c12cf0fc05057de6613d000f911c6be32b9" } } ], "extra": [ 1, 142, 116, 71, 78, 118, 218, 196, 111, 226, 100, 180, 10, 106, 89, 208, 174, 215, 200, 88, 59, 237, 207, 197, 192, 77, 154, 40, 70, 116, 34, 118, 124, 2, 17, 0, 0, 0, 2, 221, 211, 219, 145, 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