Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7609d12630148b0429b33881e9532d24e0ce95d803a9e476f94bb256a77da01

Tx prefix hash: 7c8b17bbb861f78cc83acfe60d6ee699a998883ab0cecb79a3684ebbe4a6db2c
Tx public key: 7a09326d404d8cc4c7861c7ab3734e9a846bd5ad638184c170d21e8e6427bba8
Timestamp: 1724199907 Timestamp [UCT]: 2024-08-21 00:25:07 Age [y:d:h:m:s]: 00:232:03:05:56
Block: 1092381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165769 RingCT/type: yes/0
Extra: 017a09326d404d8cc4c7861c7ab3734e9a846bd5ad638184c170d21e8e6427bba8021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf0cff98b86487b31b0555a719b2dbea2582398ed4b705dc4136650c400251e 0.600000000000 1567114 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": 1092391, "vin": [ { "gen": { "height": 1092381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf0cff98b86487b31b0555a719b2dbea2582398ed4b705dc4136650c400251e" } } ], "extra": [ 1, 122, 9, 50, 109, 64, 77, 140, 196, 199, 134, 28, 122, 179, 115, 78, 154, 132, 107, 213, 173, 99, 129, 132, 193, 112, 210, 30, 142, 100, 39, 187, 168, 2, 17, 0, 0, 0, 5, 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