Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6db57c86b59125ec0bf1dd240b26748247b78c123b0d8d5f6a197397c814d81e

Tx prefix hash: ee2106e6e58ec1e61e17c8666785b7aafb591c3009f45529d94bc53becaaeb81
Tx public key: 36cd535dd5f33d67416edf86437cdbeeb86ba831adb50e3902a3c583e4c0edbc
Timestamp: 1724710273 Timestamp [UCT]: 2024-08-26 22:11:13 Age [y:d:h:m:s]: 00:214:09:02:59
Block: 1096597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153075 RingCT/type: yes/0
Extra: 0136cd535dd5f33d67416edf86437cdbeeb86ba831adb50e3902a3c583e4c0edbc021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca66552f903ee884e0fe66018b1ee8b71d3a521dcf8b55d226e1b7c614e4332b 0.600000000000 1571788 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": 1096607, "vin": [ { "gen": { "height": 1096597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca66552f903ee884e0fe66018b1ee8b71d3a521dcf8b55d226e1b7c614e4332b" } } ], "extra": [ 1, 54, 205, 83, 93, 213, 243, 61, 103, 65, 110, 223, 134, 67, 124, 219, 238, 184, 107, 168, 49, 173, 181, 14, 57, 2, 163, 197, 131, 228, 192, 237, 188, 2, 17, 0, 0, 0, 7, 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