Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82127b0a6464cfe9f0f5b03d3e21c2983badc40a5e9a4945ff0846ff18e6da0d

Tx prefix hash: 223a20e526205f80ef8f4358729230024cd7c4161e280917506049f4177c8324
Tx public key: 8f00d533c30f4ac09cc84b47ae8428d5823e5e725c7433a5a3db1dd603db6fe4
Timestamp: 1738184211 Timestamp [UCT]: 2025-01-29 20:56:51 Age [y:d:h:m:s]: 00:138:11:42:52
Block: 1207902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98941 RingCT/type: yes/0
Extra: 018f00d533c30f4ac09cc84b47ae8428d5823e5e725c7433a5a3db1dd603db6fe40211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe940a45ce4fe074b5620cfa23b7ee836e5e0c22fc2c1eddd39efbb103a6300b 0.600000000000 1694629 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": 1207912, "vin": [ { "gen": { "height": 1207902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe940a45ce4fe074b5620cfa23b7ee836e5e0c22fc2c1eddd39efbb103a6300b" } } ], "extra": [ 1, 143, 0, 213, 51, 195, 15, 74, 192, 156, 200, 75, 71, 174, 132, 40, 213, 130, 62, 94, 114, 92, 116, 51, 165, 163, 219, 29, 214, 3, 219, 111, 228, 2, 17, 0, 0, 0, 6, 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