Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a678bded30a0987b4434900a7d63101f328e2d521ecd68b8977f064da5edf5c

Tx prefix hash: 5ca2fedbb5bc3a4a2c5b5f23e1ea6c58ef04b8cc73624f71fd0cce2faa93b2e1
Tx public key: a35bdc71fce5fa64d1dc03a18881c77de7f2f5924038946ad2d11151b08e11ff
Timestamp: 1717099990 Timestamp [UCT]: 2024-05-30 20:13:10 Age [y:d:h:m:s]: 00:299:17:13:45
Block: 1033514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214194 RingCT/type: yes/0
Extra: 01a35bdc71fce5fa64d1dc03a18881c77de7f2f5924038946ad2d11151b08e11ff0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6802cdc1e74a81efa4d9af399f6074e901645154e88016d26a25759d97abeddc 0.600000000000 1501983 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": 1033524, "vin": [ { "gen": { "height": 1033514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6802cdc1e74a81efa4d9af399f6074e901645154e88016d26a25759d97abeddc" } } ], "extra": [ 1, 163, 91, 220, 113, 252, 229, 250, 100, 209, 220, 3, 161, 136, 129, 199, 125, 231, 242, 245, 146, 64, 56, 148, 106, 210, 209, 17, 81, 176, 142, 17, 255, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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