Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c0745cf4918ef44caf7f34459437a4823ad9d5b587f1bb843e1c3358213a700

Tx prefix hash: 456d6190c63993ef9ea8144b0303d861e74717933b8b08d56a498d6ac120b341
Tx public key: ca7c74196ce0e67f5a26edcc0759fbc51803112282ffe17e8a62e1fd1ba0f5bf
Timestamp: 1574525647 Timestamp [UCT]: 2019-11-23 16:14:07 Age [y:d:h:m:s]: 04:192:14:05:10
Block: 15699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1019558 RingCT/type: yes/0
Extra: 01ca7c74196ce0e67f5a26edcc0759fbc51803112282ffe17e8a62e1fd1ba0f5bf021100000007f95225a5000000000000000000

1 output(s) for total of 544.494125387000 dcy

stealth address amount amount idx
00: bcee7c00cfc83ea397c06f32685d77e8c9266586dfcb9a114f70670b7f164746 544.494125387000 21254 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": 15709, "vin": [ { "gen": { "height": 15699 } } ], "vout": [ { "amount": 544494125387, "target": { "key": "bcee7c00cfc83ea397c06f32685d77e8c9266586dfcb9a114f70670b7f164746" } } ], "extra": [ 1, 202, 124, 116, 25, 108, 224, 230, 127, 90, 38, 237, 204, 7, 89, 251, 197, 24, 3, 17, 34, 130, 255, 225, 126, 138, 98, 225, 253, 27, 160, 245, 191, 2, 17, 0, 0, 0, 7, 249, 82, 37, 165, 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