Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86c6cba1b9ddc1fa0486bf49aabeea406d975773df1ab71facd207ddbe44fcb5

Tx prefix hash: bf4f67c61795e3d53c5453cb0a898e65be2eda5a188ae19ab235726535b8db4e
Tx public key: 24f8da51ff824adca1e1f596827c4ba8bb4b851e9e3b536d5a7547e24d465470
Timestamp: 1575811347 Timestamp [UCT]: 2019-12-08 13:22:27 Age [y:d:h:m:s]: 05:024:09:53:22
Block: 23236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163520 RingCT/type: yes/0
Extra: 0124f8da51ff824adca1e1f596827c4ba8bb4b851e9e3b536d5a7547e24d4654700211000000074943cd9f000000000000000000

1 output(s) for total of 514.064782320000 dcy

stealth address amount amount idx
00: 8e9c7f96e0f2a09839a9d7cebed9daaf421e9e16e93c1ea515fca92bb0d1a1a3 514.064782320000 37071 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": 23246, "vin": [ { "gen": { "height": 23236 } } ], "vout": [ { "amount": 514064782320, "target": { "key": "8e9c7f96e0f2a09839a9d7cebed9daaf421e9e16e93c1ea515fca92bb0d1a1a3" } } ], "extra": [ 1, 36, 248, 218, 81, 255, 130, 74, 220, 161, 225, 245, 150, 130, 124, 75, 168, 187, 75, 133, 30, 158, 59, 83, 109, 90, 117, 71, 226, 77, 70, 84, 112, 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