Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c58ae660f4dad52e5f008378c2f1bc64fc0f131510f2e49b6a10816f175f0021

Tx prefix hash: 873f8f7ec07abba56b88800b26cfa8f8db627d5a1c4096326ea447579690bf36
Tx public key: 31390b21599dd19e22c5a3eb098358d5eaf8f2382eb5ae9338edaa130f8ad6d4
Timestamp: 1718788020 Timestamp [UCT]: 2024-06-19 09:07:00 Age [y:d:h:m:s]: 00:294:20:41:27
Block: 1047510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210704 RingCT/type: yes/0
Extra: 0131390b21599dd19e22c5a3eb098358d5eaf8f2382eb5ae9338edaa130f8ad6d402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00e0937742eb2af2ba5d751e81ffed90d8c6e242450731421a9045e41e7d074a 0.600000000000 1517353 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": 1047520, "vin": [ { "gen": { "height": 1047510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00e0937742eb2af2ba5d751e81ffed90d8c6e242450731421a9045e41e7d074a" } } ], "extra": [ 1, 49, 57, 11, 33, 89, 157, 209, 158, 34, 197, 163, 235, 9, 131, 88, 213, 234, 248, 242, 56, 46, 181, 174, 147, 56, 237, 170, 19, 15, 138, 214, 212, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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