Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4990d96e1f5f481dff4df4295ea3beb7cc9fd8eb5b0007db58b1531276292d17

Tx prefix hash: bb5ea1f9a1dcc659093718e4c642f9e363ef03808167921d99d00c0dae19a619
Tx public key: 4504e75d6caf536aed506b7ea7e2d65b903547027f1b15ef3473f8a8213fa2ca
Timestamp: 1588737266 Timestamp [UCT]: 2020-05-06 03:54:26 Age [y:d:h:m:s]: 05:183:01:40:13
Block: 99132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1305445 RingCT/type: yes/0
Extra: 014504e75d6caf536aed506b7ea7e2d65b903547027f1b15ef3473f8a8213fa2ca02110000013f86362411000000000000000000

1 output(s) for total of 288.094717759000 dcy

stealth address amount amount idx
00: f320c06a83f5a31e765292ef7170736f1f2d4b63aec6d08f40abbd237c577dbe 288.094717759000 174978 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": 99142, "vin": [ { "gen": { "height": 99132 } } ], "vout": [ { "amount": 288094717759, "target": { "key": "f320c06a83f5a31e765292ef7170736f1f2d4b63aec6d08f40abbd237c577dbe" } } ], "extra": [ 1, 69, 4, 231, 93, 108, 175, 83, 106, 237, 80, 107, 126, 167, 226, 214, 91, 144, 53, 71, 2, 127, 27, 21, 239, 52, 115, 248, 168, 33, 63, 162, 202, 2, 17, 0, 0, 1, 63, 134, 54, 36, 17, 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