Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37420ff74a3d87d3e323318edb70d296f610d3c394e8ea289d9e85c3249fc0b3

Tx prefix hash: 3e1b4c98112818b6f4e993e715a7a04b21f494ca60c85e86bce398a421a6bced
Tx public key: 4071f045ba67ef0f100f0593fa8a06a29f144853deef27bd69f0b03199ba31ac
Timestamp: 1711250577 Timestamp [UCT]: 2024-03-24 03:22:57 Age [y:d:h:m:s]: 01:006:02:14:08
Block: 985035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265310 RingCT/type: yes/0
Extra: 014071f045ba67ef0f100f0593fa8a06a29f144853deef27bd69f0b03199ba31ac02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88e5ef0eee997a3a8f27ca7e8c558fe3be9c0e302c7c0f17825ea62d399fb575 0.600000000000 1445240 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": 985045, "vin": [ { "gen": { "height": 985035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88e5ef0eee997a3a8f27ca7e8c558fe3be9c0e302c7c0f17825ea62d399fb575" } } ], "extra": [ 1, 64, 113, 240, 69, 186, 103, 239, 15, 16, 15, 5, 147, 250, 138, 6, 162, 159, 20, 72, 83, 222, 239, 39, 189, 105, 240, 176, 49, 153, 186, 49, 172, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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