Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35f8d71ed7c7891096854aacf2af326363d00f56db7beb353d3054062871e98a

Tx prefix hash: c211bf517f4aad3e33b313377e70a51debb6f14e7a87e466d0f32d2b34f97053
Tx public key: a42270e8455999f410fe6d16c7d66865597d3bd1735e47dcee83adc2dbeff806
Timestamp: 1634637881 Timestamp [UCT]: 2021-10-19 10:04:41 Age [y:d:h:m:s]: 03:190:17:28:17
Block: 356097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 914215 RingCT/type: yes/0
Extra: 01a42270e8455999f410fe6d16c7d66865597d3bd1735e47dcee83adc2dbeff806021100000002f29d7abf000000000000000000

1 output(s) for total of 40.560493532000 dcy

stealth address amount amount idx
00: cc9970cd59bd85d793b8fd872e0f516da69b42204efb0f7eaa201f5e469d5a60 40.560493532000 726697 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": 356107, "vin": [ { "gen": { "height": 356097 } } ], "vout": [ { "amount": 40560493532, "target": { "key": "cc9970cd59bd85d793b8fd872e0f516da69b42204efb0f7eaa201f5e469d5a60" } } ], "extra": [ 1, 164, 34, 112, 232, 69, 89, 153, 244, 16, 254, 109, 22, 199, 214, 104, 101, 89, 125, 59, 209, 115, 94, 71, 220, 238, 131, 173, 194, 219, 239, 248, 6, 2, 17, 0, 0, 0, 2, 242, 157, 122, 191, 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