Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9718ff602478333f37fe5d7d0575525b97b6cad4ca6698b7280b31a148bfe6f3

Tx prefix hash: 88b6ab5ce16e03c1aab199f8a1735e85485530a34a596c4e7ebc7bb0bae099d7
Tx public key: caaddcba88ab5189ec658d976e50eb230bcf44e94982066b9aeaf6ff0ea4a2a8
Timestamp: 1722700008 Timestamp [UCT]: 2024-08-03 15:46:48 Age [y:d:h:m:s]: 00:298:23:59:17
Block: 1079935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213642 RingCT/type: yes/0
Extra: 01caaddcba88ab5189ec658d976e50eb230bcf44e94982066b9aeaf6ff0ea4a2a8021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 999a1c14f12fe9890011e47ee652d3b2ca9b96c3a039bf7b50e8dee9def9093c 0.600000000000 1553100 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": 1079945, "vin": [ { "gen": { "height": 1079935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "999a1c14f12fe9890011e47ee652d3b2ca9b96c3a039bf7b50e8dee9def9093c" } } ], "extra": [ 1, 202, 173, 220, 186, 136, 171, 81, 137, 236, 101, 141, 151, 110, 80, 235, 35, 11, 207, 68, 233, 73, 130, 6, 107, 154, 234, 246, 255, 14, 164, 162, 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