Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9218b32e9b1b3ad4fc4954dd4b4c3f07091412023db41a10948909236c6e9ca0

Tx prefix hash: 545c38c8b6a782618e540689d3d1414c3c6ed338c3b050f1934832f051506904
Tx public key: ce61eac6c14a2d48e9fe109fd5b19a996e85984fcc49a32c5b138186a8fef52d
Timestamp: 1751431790 Timestamp [UCT]: 2025-07-02 04:49:50 Age [y:d:h:m:s]: 00:142:18:33:07
Block: 1317004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100269 RingCT/type: yes/0
Extra: 01ce61eac6c14a2d48e9fe109fd5b19a996e85984fcc49a32c5b138186a8fef52d02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b3fb531deaa54afbbcd0b8a9bf0955dc7810ad3e43da107ff93256b9f2acd56 0.600000000000 1804669 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": 1317014, "vin": [ { "gen": { "height": 1317004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b3fb531deaa54afbbcd0b8a9bf0955dc7810ad3e43da107ff93256b9f2acd56" } } ], "extra": [ 1, 206, 97, 234, 198, 193, 74, 45, 72, 233, 254, 16, 159, 213, 177, 154, 153, 110, 133, 152, 79, 204, 73, 163, 44, 91, 19, 129, 134, 168, 254, 245, 45, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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