Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a05887491806eb4528b91a533b7bd8bea2c458f473b614bd5b306cc60c087d28

Tx prefix hash: 1ae81270d46d455d3b850e96ab18ffff3cd97dd03b4fa9a49e39cad5662aed6c
Tx public key: 329f1aeaf5a1c5ac11057339c5d5183ba702d3611195ed5de282dab37f70f79f
Timestamp: 1735673322 Timestamp [UCT]: 2024-12-31 19:28:42 Age [y:d:h:m:s]: 00:173:00:41:38
Block: 1187363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123286 RingCT/type: yes/0
Extra: 01329f1aeaf5a1c5ac11057339c5d5183ba702d3611195ed5de282dab37f70f79f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 462b842b6ed430bb369608f0b0c0e6589e06db78c03b16f8c37664aa0b6c3dfc 0.600000000000 1673852 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": 1187373, "vin": [ { "gen": { "height": 1187363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "462b842b6ed430bb369608f0b0c0e6589e06db78c03b16f8c37664aa0b6c3dfc" } } ], "extra": [ 1, 50, 159, 26, 234, 245, 161, 197, 172, 17, 5, 115, 57, 197, 213, 24, 59, 167, 2, 211, 97, 17, 149, 237, 93, 226, 130, 218, 179, 127, 112, 247, 159, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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