Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cda41508c6d50b94737b83305e3f9f8d258151c8ba0d5b27426b91bcfd2ff6f

Tx prefix hash: 9dc66e3d9f6586dd1d032b6e48a39a8eb1f594830768be6d5ead3efbaf137654
Tx public key: 7994197c7291ef2cd426ad87f6d34a6c04d599a1d068bd84b0aa59ead929f832
Timestamp: 1750991518 Timestamp [UCT]: 2025-06-27 02:31:58 Age [y:d:h:m:s]: 00:196:09:25:59
Block: 1313579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138451 RingCT/type: yes/0
Extra: 017994197c7291ef2cd426ad87f6d34a6c04d599a1d068bd84b0aa59ead929f832021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f015e740a01a89e4b51608175e34dd139d27fdb2e9ae4c38cf8b424de0434f6b 0.600000000000 1801220 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": 1313589, "vin": [ { "gen": { "height": 1313579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f015e740a01a89e4b51608175e34dd139d27fdb2e9ae4c38cf8b424de0434f6b" } } ], "extra": [ 1, 121, 148, 25, 124, 114, 145, 239, 44, 212, 38, 173, 135, 246, 211, 74, 108, 4, 213, 153, 161, 208, 104, 189, 132, 176, 170, 89, 234, 217, 41, 248, 50, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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