Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbbb610f361f1aed2d532e6917c4357c52eba25ac472aa755824dbc501036d6f

Tx prefix hash: 9e09624f7b6d77ac9fa49e87bfe39145c1b1f5967635ec9ec5d153683d1500ee
Tx public key: 0adabe0f5b4bbf53be4c8253d5ed121dec34dd45b94d9bb7f55c51d93ec9ed15
Timestamp: 1581949244 Timestamp [UCT]: 2020-02-17 14:20:44 Age [y:d:h:m:s]: 04:323:11:55:39
Block: 66844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123596 RingCT/type: yes/0
Extra: 010adabe0f5b4bbf53be4c8253d5ed121dec34dd45b94d9bb7f55c51d93ec9ed15021100000001c71d3ff9000000000000000000

1 output(s) for total of 368.569071058000 dcy

stealth address amount amount idx
00: c0841533ef58de80200ecfb60c67b9a52844c45abf90f93ecf258cd377b6dac1 368.569071058000 123061 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": 66854, "vin": [ { "gen": { "height": 66844 } } ], "vout": [ { "amount": 368569071058, "target": { "key": "c0841533ef58de80200ecfb60c67b9a52844c45abf90f93ecf258cd377b6dac1" } } ], "extra": [ 1, 10, 218, 190, 15, 91, 75, 191, 83, 190, 76, 130, 83, 213, 237, 18, 29, 236, 52, 221, 69, 185, 77, 155, 183, 245, 92, 81, 217, 62, 201, 237, 21, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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