Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 947a917f5e3b0aa0e7ae17e55725fd510102b0a7c8367099b67b7b8335ba6a55

Tx prefix hash: 58e89681de06acebf4f6887b372306083c05f7fe7a121e42a63e39b98eddfff8
Tx public key: 7d01ee71a6df3d8cb89f4427f496682bae9c30e61968e90356f97ff96101ebf8
Timestamp: 1720657378 Timestamp [UCT]: 2024-07-11 00:22:58 Age [y:d:h:m:s]: 00:246:18:54:45
Block: 1063013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176314 RingCT/type: yes/0
Extra: 017d01ee71a6df3d8cb89f4427f496682bae9c30e61968e90356f97ff96101ebf8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 224bf2b1ecb05b31e15039a78fe21e7c69070cf3780f744e2c2e946d83d44de1 0.600000000000 1533524 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": 1063023, "vin": [ { "gen": { "height": 1063013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "224bf2b1ecb05b31e15039a78fe21e7c69070cf3780f744e2c2e946d83d44de1" } } ], "extra": [ 1, 125, 1, 238, 113, 166, 223, 61, 140, 184, 159, 68, 39, 244, 150, 104, 43, 174, 156, 48, 230, 25, 104, 233, 3, 86, 249, 127, 249, 97, 1, 235, 248, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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