Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118ce907b4c0879524855ce1da2b4c8ed683557fe2b0c70eb96270862f347d46

Tx prefix hash: 6a6d2cf329c6b5a57f72fcf4acedd0e583861101141603b4a5023f3c8b4a572d
Tx public key: bd0e0f213b5a8983c39a4323afde59c843b1a2c387a4580b1b8fb9c0d4168f2a
Timestamp: 1753260242 Timestamp [UCT]: 2025-07-23 08:44:02 Age [y:d:h:m:s]: 00:114:12:30:32
Block: 1331536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80671 RingCT/type: yes/0
Extra: 01bd0e0f213b5a8983c39a4323afde59c843b1a2c387a4580b1b8fb9c0d4168f2a02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37467ceba2a756607d0d239d5ad44d9baa6e2c09fda83b225e4a294e4ca3f222 0.600000000000 1819331 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": 1331546, "vin": [ { "gen": { "height": 1331536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37467ceba2a756607d0d239d5ad44d9baa6e2c09fda83b225e4a294e4ca3f222" } } ], "extra": [ 1, 189, 14, 15, 33, 59, 90, 137, 131, 195, 154, 67, 35, 175, 222, 89, 200, 67, 177, 162, 195, 135, 164, 88, 11, 27, 143, 185, 192, 212, 22, 143, 42, 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