Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eeea8538589b36fe3b10f2599c29e5aaebe2ac467c9365933923cedeff33561

Tx prefix hash: c3739a6a6bffc89dfc5f01d1b04eb687476b5f264d50f6f139968541d16d12f1
Tx public key: bb09c5b01dddb5e8a478b95bb81c3365972cfd8d07199e1190385d01e9ba6a0f
Timestamp: 1602086082 Timestamp [UCT]: 2020-10-07 15:54:42 Age [y:d:h:m:s]: 04:125:00:09:00
Block: 140120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074775 RingCT/type: yes/0
Extra: 01bb09c5b01dddb5e8a478b95bb81c3365972cfd8d07199e1190385d01e9ba6a0f0211000013333a3a2186000000000000000000

1 output(s) for total of 210.729326244000 dcy

stealth address amount amount idx
00: 8e11ea112433d6014645e2a7de6cd55b46f18d661796c09ec7a64a789ea741e2 210.729326244000 232757 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": 140130, "vin": [ { "gen": { "height": 140120 } } ], "vout": [ { "amount": 210729326244, "target": { "key": "8e11ea112433d6014645e2a7de6cd55b46f18d661796c09ec7a64a789ea741e2" } } ], "extra": [ 1, 187, 9, 197, 176, 29, 221, 181, 232, 164, 120, 185, 91, 184, 28, 51, 101, 151, 44, 253, 141, 7, 25, 158, 17, 144, 56, 93, 1, 233, 186, 106, 15, 2, 17, 0, 0, 19, 51, 58, 58, 33, 134, 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