Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce09d1409353c2ab1405455d47cd1a09a8db59a6a21a59eb3dbf39211cd3b7dd

Tx prefix hash: 17d8eec64129e62e789b7431e1d2b863535fd1c42f4082a2237404ab6ad5beb5
Tx public key: a8cd2614a8d321f405d3434a8d186ef6be04118ee9fa40fcae5cccb41f29b88f
Timestamp: 1712671554 Timestamp [UCT]: 2024-04-09 14:05:54 Age [y:d:h:m:s]: 01:033:10:47:42
Block: 996771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284900 RingCT/type: yes/0
Extra: 01a8cd2614a8d321f405d3434a8d186ef6be04118ee9fa40fcae5cccb41f29b88f021100000002bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34c8bed350201829948e09992e3a314c6f0fd298ace6b82e224acf70a69c4579 0.600000000000 1457199 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": 996781, "vin": [ { "gen": { "height": 996771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34c8bed350201829948e09992e3a314c6f0fd298ace6b82e224acf70a69c4579" } } ], "extra": [ 1, 168, 205, 38, 20, 168, 211, 33, 244, 5, 211, 67, 74, 141, 24, 110, 246, 190, 4, 17, 142, 233, 250, 64, 252, 174, 92, 204, 180, 31, 41, 184, 143, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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