Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31b0c4d7c8d2cef25a79880a4a990308adec1f0a19f1f379e35deea5066528fe

Tx prefix hash: d2bec4005401da7821cc5ecaa4ac74ef7a904a355b562b7903ea7484e61778b7
Tx public key: 2df8e8b2f4d45084b1da941eeb13559cae80e997c8b04d979c15b9ec1aa9e5ce
Timestamp: 1762246884 Timestamp [UCT]: 2025-11-04 09:01:24 Age [y:d:h:m:s]: 00:016:15:25:01
Block: 1404686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11896 RingCT/type: yes/0
Extra: 012df8e8b2f4d45084b1da941eeb13559cae80e997c8b04d979c15b9ec1aa9e5ce021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e3b68a8b6a3ae4673e56d4ec2482a2cf25d5bff683e1dfdc888d8e1b77e91cf 0.600000000000 1893045 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": 1404696, "vin": [ { "gen": { "height": 1404686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e3b68a8b6a3ae4673e56d4ec2482a2cf25d5bff683e1dfdc888d8e1b77e91cf" } } ], "extra": [ 1, 45, 248, 232, 178, 244, 212, 80, 132, 177, 218, 148, 30, 235, 19, 85, 156, 174, 128, 233, 151, 200, 176, 77, 151, 156, 21, 185, 236, 26, 169, 229, 206, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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