Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0c86ab1287d044a4e1ab3ce80b8a5f862a5c44b96e889321cde4ac188faa3ac

Tx prefix hash: 4d958488b130e4d6aef77db49ca90ea613bdadf25b5410de4c59854aff8741a1
Tx public key: 230dcec698f6f4e55ebd6035a429f8cc17b14c27cec161716fbdd49ceb8ee2c3
Timestamp: 1760885149 Timestamp [UCT]: 2025-10-19 14:45:49 Age [y:d:h:m:s]: 00:098:15:13:37
Block: 1393412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70426 RingCT/type: yes/0
Extra: 01230dcec698f6f4e55ebd6035a429f8cc17b14c27cec161716fbdd49ceb8ee2c302110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30863637b34f4cc7683ba089d7079066ec4d4c212e7c2a0b95bbc0d445db9139 0.600000000000 1881677 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": 1393422, "vin": [ { "gen": { "height": 1393412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30863637b34f4cc7683ba089d7079066ec4d4c212e7c2a0b95bbc0d445db9139" } } ], "extra": [ 1, 35, 13, 206, 198, 152, 246, 244, 229, 94, 189, 96, 53, 164, 41, 248, 204, 23, 177, 76, 39, 206, 193, 97, 113, 111, 189, 212, 156, 235, 142, 226, 195, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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