Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4409b802f892c724fb86f3dad81b6b1cfe3a55592a85bc6531fde95fb5ee7ef8

Tx prefix hash: d6628ddac3b2c4470dce9fe785f6ab2f63f1be21f0a6ab8a88bdb9bf6746122b
Tx public key: 05b72413bd899dc807f3641fba50c27f3e319ff5216109a74ae8ab68b8b1112f
Timestamp: 1736644921 Timestamp [UCT]: 2025-01-12 01:22:01 Age [y:d:h:m:s]: 00:065:05:59:17
Block: 1195409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46408 RingCT/type: yes/0
Extra: 0105b72413bd899dc807f3641fba50c27f3e319ff5216109a74ae8ab68b8b1112f0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98d81729895a03882e03f838f277c87fdda7f2b85463dbf2244d4715cb46dca 0.600000000000 1681998 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": 1195419, "vin": [ { "gen": { "height": 1195409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98d81729895a03882e03f838f277c87fdda7f2b85463dbf2244d4715cb46dca" } } ], "extra": [ 1, 5, 183, 36, 19, 189, 137, 157, 200, 7, 243, 100, 31, 186, 80, 194, 127, 62, 49, 159, 245, 33, 97, 9, 167, 74, 232, 171, 104, 184, 177, 17, 47, 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