Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9df0616dd83a0faaaaf96dc4966995c5b075edb498b90c7a84e1e630af366d

Tx prefix hash: 57ce66d55125c97c4f1e81c21bcc9a66b0ebb0555dd01dcaf76acac2035c97d2
Tx public key: c8ea7878b617f6305630542c2efc59fed1876f33c58881f65b9e5cef621cfc33
Timestamp: 1749714476 Timestamp [UCT]: 2025-06-12 07:47:56 Age [y:d:h:m:s]: 00:151:20:55:58
Block: 1303307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106252 RingCT/type: yes/0
Extra: 01c8ea7878b617f6305630542c2efc59fed1876f33c58881f65b9e5cef621cfc33021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c38f85239bd57598a548f314579d3e459e5a6139ce7ad8af62958e22585f3f4 0.600000000000 1790886 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": 1303317, "vin": [ { "gen": { "height": 1303307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c38f85239bd57598a548f314579d3e459e5a6139ce7ad8af62958e22585f3f4" } } ], "extra": [ 1, 200, 234, 120, 120, 182, 23, 246, 48, 86, 48, 84, 44, 46, 252, 89, 254, 209, 135, 111, 51, 197, 136, 129, 246, 91, 158, 92, 239, 98, 28, 252, 51, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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