Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4205dab43d5e3dd5272eea3defda4611f48af3e63890930b578a42272d63a7d0

Tx prefix hash: f36e70c19b3b978cd0d9f47cd68f6172adff0f3ce6938b40869fbd18cb19f234
Tx public key: 868d83360a6623f885f993cf98783d99010215d6638cf1a3e6d37ab8d1bec69b
Timestamp: 1577734557 Timestamp [UCT]: 2019-12-30 19:35:57 Age [y:d:h:m:s]: 04:363:13:21:13
Block: 35281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148903 RingCT/type: yes/0
Extra: 01868d83360a6623f885f993cf98783d99010215d6638cf1a3e6d37ab8d1bec69b0211000000074943cd9f000000000000000000

1 output(s) for total of 468.921618940000 dcy

stealth address amount amount idx
00: 0cc828d893e2ef88851b1467a427330b7a450226364b34aa7a3db9596a8b7dbe 468.921618940000 59413 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": 35291, "vin": [ { "gen": { "height": 35281 } } ], "vout": [ { "amount": 468921618940, "target": { "key": "0cc828d893e2ef88851b1467a427330b7a450226364b34aa7a3db9596a8b7dbe" } } ], "extra": [ 1, 134, 141, 131, 54, 10, 102, 35, 248, 133, 249, 147, 207, 152, 120, 61, 153, 1, 2, 21, 214, 99, 140, 241, 163, 230, 211, 122, 184, 209, 190, 198, 155, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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