Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1e93b5cf8c2ad57f88e0ee0dec88f9f473ca1e312991ea494f0cd0612352f04

Tx prefix hash: 4d61d6900aa6c6567f03870d6c41a9327adec4e531fd3eed6acce752445df7e0
Tx public key: 0d73a5e0aaa4b2ec346eb5b1af637968a7f007131834a635b64502c133a97ab3
Timestamp: 1751322125 Timestamp [UCT]: 2025-06-30 22:22:05 Age [y:d:h:m:s]: 00:143:22:53:48
Block: 1316133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101081 RingCT/type: yes/0
Extra: 010d73a5e0aaa4b2ec346eb5b1af637968a7f007131834a635b64502c133a97ab3021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54ab1de3dd2c67c57efe66f3d16540234a915d5342045ddcdda0cac2cba4664a 0.600000000000 1803790 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": 1316143, "vin": [ { "gen": { "height": 1316133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54ab1de3dd2c67c57efe66f3d16540234a915d5342045ddcdda0cac2cba4664a" } } ], "extra": [ 1, 13, 115, 165, 224, 170, 164, 178, 236, 52, 110, 181, 177, 175, 99, 121, 104, 167, 240, 7, 19, 24, 52, 166, 53, 182, 69, 2, 193, 51, 169, 122, 179, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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