Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef6ceca9e44cf16c3d26be21c1291e0824e7784684136ae683acdd0d8bb0566

Tx prefix hash: 949b22440f2a6a8504c1d3606993689eb7c259fa5272fe115da45b8420333ba3
Tx public key: a6ae7d5f9ee9e2ed02fd0e6f26cd3ea719ee9bfb679c80b6869f8a911dc3a11b
Timestamp: 1583347695 Timestamp [UCT]: 2020-03-04 18:48:15 Age [y:d:h:m:s]: 04:257:17:42:57
Block: 76523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078454 RingCT/type: yes/0
Extra: 01a6ae7d5f9ee9e2ed02fd0e6f26cd3ea719ee9bfb679c80b6869f8a911dc3a11b0211000000350aca7173000000000000000000

1 output(s) for total of 342.332656190000 dcy

stealth address amount amount idx
00: 63f77f7bee6ad6c41aeac17629a97107274c6fc14478c1c37642deb3683c19be 342.332656190000 140793 of 0

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": 76533, "vin": [ { "gen": { "height": 76523 } } ], "vout": [ { "amount": 342332656190, "target": { "key": "63f77f7bee6ad6c41aeac17629a97107274c6fc14478c1c37642deb3683c19be" } } ], "extra": [ 1, 166, 174, 125, 95, 158, 233, 226, 237, 2, 253, 14, 111, 38, 205, 62, 167, 25, 238, 155, 251, 103, 156, 128, 182, 134, 159, 138, 145, 29, 195, 161, 27, 2, 17, 0, 0, 0, 53, 10, 202, 113, 115, 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