Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b113bb340e3897a9316dcee5cfbd07fb5d26ab4cbab2664b3f1b59140c280185

Tx prefix hash: d8968dd00cee60162494e493eb8e0dc69a6ab467bc09ab54c605f8f5ad961a7d
Tx public key: f1aa7711ffd45e16f8bb51a6703dbc336fef4ae7b4f07e8706e28ddd0a67542b
Timestamp: 1761198920 Timestamp [UCT]: 2025-10-23 05:55:20 Age [y:d:h:m:s]: 00:018:13:51:45
Block: 1396008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13290 RingCT/type: yes/0
Extra: 01f1aa7711ffd45e16f8bb51a6703dbc336fef4ae7b4f07e8706e28ddd0a67542b02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2225caa8e40386d6893bb9617df83dbc816c649f224ab4a3a80044c7eed830e1 0.600000000000 1884291 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": 1396018, "vin": [ { "gen": { "height": 1396008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2225caa8e40386d6893bb9617df83dbc816c649f224ab4a3a80044c7eed830e1" } } ], "extra": [ 1, 241, 170, 119, 17, 255, 212, 94, 22, 248, 187, 81, 166, 112, 61, 188, 51, 111, 239, 74, 231, 180, 240, 126, 135, 6, 226, 141, 221, 10, 103, 84, 43, 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