Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3ecbd26cd9e52618887cf033d0f31cc24c3b6610f2f3af681629aed26bd7728

Tx prefix hash: 23c85749c79960d67b375cd8b9b24f380cc1fb9dc05976f9c0a9a62bbd000c4c
Tx public key: 9cc42ab78cb671ca75a0be3f69573debe96c28c054ba1315b9578c5efa484aa7
Timestamp: 1705085918 Timestamp [UCT]: 2024-01-12 18:58:38 Age [y:d:h:m:s]: 01:076:21:23:11
Block: 933895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316051 RingCT/type: yes/0
Extra: 019cc42ab78cb671ca75a0be3f69573debe96c28c054ba1315b9578c5efa484aa702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a54520a319681f9b10692e4b63b419bf62fdd8f8e48e4f16b0ce8228009afdc1 0.600000000000 1391879 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": 933905, "vin": [ { "gen": { "height": 933895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a54520a319681f9b10692e4b63b419bf62fdd8f8e48e4f16b0ce8228009afdc1" } } ], "extra": [ 1, 156, 196, 42, 183, 140, 182, 113, 202, 117, 160, 190, 63, 105, 87, 61, 235, 233, 108, 40, 192, 84, 186, 19, 21, 185, 87, 140, 94, 250, 72, 74, 167, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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