Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e29850bfc9bc377488cc8e0fb161b7405bf7210a54fa2ed3e2698508b4cd4ba

Tx prefix hash: 3b4f51e482ad8433a8f4fbab40f20ea010713d6d2984274586efcc3538c1e02d
Tx public key: f8c3afdbbbb75c7a3ec7564e657dd69e5d71ea1d9e1eca4b5ebf5be243110720
Timestamp: 1701164998 Timestamp [UCT]: 2023-11-28 09:49:58 Age [y:d:h:m:s]: 01:087:23:43:09
Block: 901399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324009 RingCT/type: yes/0
Extra: 01f8c3afdbbbb75c7a3ec7564e657dd69e5d71ea1d9e1eca4b5ebf5be2431107200211000000014b8f5122000000000000000000

1 output(s) for total of 0.632835605000 dcy

stealth address amount amount idx
00: 7847b426dd6ad1341f536d461d31316fbfd11a4dc74554daa02712816816462c 0.632835605000 1357958 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": 901409, "vin": [ { "gen": { "height": 901399 } } ], "vout": [ { "amount": 632835605, "target": { "key": "7847b426dd6ad1341f536d461d31316fbfd11a4dc74554daa02712816816462c" } } ], "extra": [ 1, 248, 195, 175, 219, 187, 183, 92, 122, 62, 199, 86, 78, 101, 125, 214, 158, 93, 113, 234, 29, 158, 30, 202, 75, 94, 191, 91, 226, 67, 17, 7, 32, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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