Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34cb3a3f24e75f3cfd8741aa71ffcb524d90f74716a6776372f3334bf72c8c5

Tx prefix hash: db4347eff6e12317a0419a254118d1e81e7e508b2f1c8da738d86eec6f0c35e4
Tx public key: 10d900adf87e37e4d40e319e830517dfcad636a4a07774a1bfc70aba90548eee
Timestamp: 1694702049 Timestamp [UCT]: 2023-09-14 14:34:09 Age [y:d:h:m:s]: 01:193:12:01:18
Block: 848011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399369 RingCT/type: yes/0
Extra: 0110d900adf87e37e4d40e319e830517dfcad636a4a07774a1bfc70aba90548eee0211000000044b8f5122000000000000000000

1 output(s) for total of 0.951015489000 dcy

stealth address amount amount idx
00: 459378e4240398d46128b122d362331780d87187942aa038d10c12e9f5592d32 0.951015489000 1301587 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": 848021, "vin": [ { "gen": { "height": 848011 } } ], "vout": [ { "amount": 951015489, "target": { "key": "459378e4240398d46128b122d362331780d87187942aa038d10c12e9f5592d32" } } ], "extra": [ 1, 16, 217, 0, 173, 248, 126, 55, 228, 212, 14, 49, 158, 131, 5, 23, 223, 202, 214, 54, 164, 160, 119, 116, 161, 191, 199, 10, 186, 144, 84, 142, 238, 2, 17, 0, 0, 0, 4, 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