Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23cd202c6a1b3667f0b0dd4deb3a18cc913f1494cd9cdb64a30155d4817faf1

Tx prefix hash: d823366a3b4a47f3f4f7f6698f6192a53a24baa9a9938ebb03509bc1839c5710
Tx public key: 32319f0389e21a801e3e20d966ccdb31abceddf796e9a94b35309a942ee43b28
Timestamp: 1741045386 Timestamp [UCT]: 2025-03-03 23:43:06 Age [y:d:h:m:s]: 00:261:18:01:39
Block: 1231574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184815 RingCT/type: yes/0
Extra: 0132319f0389e21a801e3e20d966ccdb31abceddf796e9a94b35309a942ee43b28021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 516a29e2929bc150c0be60b9c76db33273026fd97af7f8e28d33a420618c6c3f 0.600000000000 1718481 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": 1231584, "vin": [ { "gen": { "height": 1231574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "516a29e2929bc150c0be60b9c76db33273026fd97af7f8e28d33a420618c6c3f" } } ], "extra": [ 1, 50, 49, 159, 3, 137, 226, 26, 128, 30, 62, 32, 217, 102, 204, 219, 49, 171, 206, 221, 247, 150, 233, 169, 75, 53, 48, 154, 148, 46, 228, 59, 40, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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