Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dcb3dbcfd00cc3253a4e525579b85f22dd8ec96fd37442780ab0b319158a255

Tx prefix hash: b19c81f098830607c7e3977c56582bf64141d8a1b7caa479080f633b68cdc2e7
Tx public key: 4da9889072b3153d14a75984d756deddb7ce696f910d80182bb4ca585f3525ff
Timestamp: 1581950638 Timestamp [UCT]: 2020-02-17 14:43:58 Age [y:d:h:m:s]: 05:013:01:56:43
Block: 66913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1162296 RingCT/type: yes/0
Extra: 014da9889072b3153d14a75984d756deddb7ce696f910d80182bb4ca585f3525ff021100000001d81c26c0000000000000000000

1 output(s) for total of 368.387526219000 dcy

stealth address amount amount idx
00: db29d062abd7cb3f9d3ac7ac074ae4474b2b4ca1db76339fc8b82b4069658b4f 368.387526219000 123164 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": 66923, "vin": [ { "gen": { "height": 66913 } } ], "vout": [ { "amount": 368387526219, "target": { "key": "db29d062abd7cb3f9d3ac7ac074ae4474b2b4ca1db76339fc8b82b4069658b4f" } } ], "extra": [ 1, 77, 169, 136, 144, 114, 179, 21, 61, 20, 167, 89, 132, 215, 86, 222, 221, 183, 206, 105, 111, 145, 13, 128, 24, 43, 180, 202, 88, 95, 53, 37, 255, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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