Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c28b12794b061c1f2ffde1d74cf294cdcae67f51c7db91c4125bd4750c3a6a0

Tx prefix hash: 5eae3936493d0ff37baa0cb0e11f7832d8ff0d6d6f95ebb618b530c9b4f40155
Tx public key: 353561f70ae8a66d3cddcb6d7e0e69b2afb9e8792287660ab57c6c5c1af752d9
Timestamp: 1747677256 Timestamp [UCT]: 2025-05-19 17:54:16 Age [y:d:h:m:s]: 00:141:08:52:51
Block: 1286475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98675 RingCT/type: yes/0
Extra: 01353561f70ae8a66d3cddcb6d7e0e69b2afb9e8792287660ab57c6c5c1af752d90211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e94d3ddee1838e760d0256190f6ebe2c3d0ab023525357456c75aad6b3333fe 0.600000000000 1773940 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": 1286485, "vin": [ { "gen": { "height": 1286475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e94d3ddee1838e760d0256190f6ebe2c3d0ab023525357456c75aad6b3333fe" } } ], "extra": [ 1, 53, 53, 97, 247, 10, 232, 166, 109, 60, 221, 203, 109, 126, 14, 105, 178, 175, 185, 232, 121, 34, 135, 102, 10, 181, 124, 108, 92, 26, 247, 82, 217, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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