Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fac49347dd74a999f039f2de8e14e75db749c352dde0087ae5c962c85b0a505f

Tx prefix hash: 9f528ac800dd619bb6c70b06748fa574d6851822285af3c5e27c3d4b84327095
Tx public key: 355121c0138efbb6e37a9e29c585ec06c1c7c02cda0cdd81182c3ef0540b5a52
Timestamp: 1762067383 Timestamp [UCT]: 2025-11-02 07:09:43 Age [y:d:h:m:s]: 00:003:08:32:35
Block: 1403201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2389 RingCT/type: yes/0
Extra: 01355121c0138efbb6e37a9e29c585ec06c1c7c02cda0cdd81182c3ef0540b5a520211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3206cbd9060b20d1cac926fd23e851d96ae7f9d841044dbba1500a07af849ce 0.600000000000 1891528 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": 1403211, "vin": [ { "gen": { "height": 1403201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3206cbd9060b20d1cac926fd23e851d96ae7f9d841044dbba1500a07af849ce" } } ], "extra": [ 1, 53, 81, 33, 192, 19, 142, 251, 182, 227, 122, 158, 41, 197, 133, 236, 6, 193, 199, 192, 44, 218, 12, 221, 129, 24, 44, 62, 240, 84, 11, 90, 82, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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