Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 543b8fddc636291a236fc1a47e25bbede0e33f25987c9d873c149142c1775c1b

Tx prefix hash: 33c1440a35e95e0282351557fd34f91391e414aa6dc75cff7fbf0e388cd8e09d
Tx public key: 32a3d86e190f62808256b30e7f876c2fd263fd859e746435f281130589aa7c36
Timestamp: 1730415483 Timestamp [UCT]: 2024-10-31 22:58:03 Age [y:d:h:m:s]: 00:185:00:12:40
Block: 1143814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132087 RingCT/type: yes/0
Extra: 0132a3d86e190f62808256b30e7f876c2fd263fd859e746435f281130589aa7c36021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91eaf16656f2ceb11413699c8d6544fec43d37e2b0edfbdeb56eea62e106f5fb 0.600000000000 1627819 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": 1143824, "vin": [ { "gen": { "height": 1143814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91eaf16656f2ceb11413699c8d6544fec43d37e2b0edfbdeb56eea62e106f5fb" } } ], "extra": [ 1, 50, 163, 216, 110, 25, 15, 98, 128, 130, 86, 179, 14, 127, 135, 108, 47, 210, 99, 253, 133, 158, 116, 100, 53, 242, 129, 19, 5, 137, 170, 124, 54, 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