Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96721019864a5d0983134f474ec2bc9f3934bc5bd80cb45e81bf9617c3795c00

Tx prefix hash: 90a112fa5d55ea48ceb645eeab1b396f6f78fc9c8eab29e7179ebc8436a07180
Tx public key: 57b4fab8df8ca6e5a1c5501c9651f505f19a957646f8ad04aec01da5cab9f95e
Timestamp: 1755712112 Timestamp [UCT]: 2025-08-20 17:48:32 Age [y:d:h:m:s]: 00:046:05:29:32
Block: 1350738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32874 RingCT/type: yes/0
Extra: 0157b4fab8df8ca6e5a1c5501c9651f505f19a957646f8ad04aec01da5cab9f95e021100000010ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31867a214fab34556e81b3c69301fe57959db4e87d17ca4300464d75d5f79ea8 0.600000000000 1838685 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": 1350748, "vin": [ { "gen": { "height": 1350738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31867a214fab34556e81b3c69301fe57959db4e87d17ca4300464d75d5f79ea8" } } ], "extra": [ 1, 87, 180, 250, 184, 223, 140, 166, 229, 161, 197, 80, 28, 150, 81, 245, 5, 241, 154, 149, 118, 70, 248, 173, 4, 174, 192, 29, 165, 202, 185, 249, 94, 2, 17, 0, 0, 0, 16, 173, 121, 72, 208, 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