Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9c76f69b382b8187b798ea6a85b4a40c03fe3d455bc1b21497cb0ee30cd07c

Tx prefix hash: 16e854f5aa4a408ae740f34651922e9600455eed152078cfca501a78eca11efa
Tx public key: 997bcc07d9e56992a5a9d614d06ba654ffeea1446ce9e00f8b9ff89c25aca926
Timestamp: 1582095016 Timestamp [UCT]: 2020-02-19 06:50:16 Age [y:d:h:m:s]: 04:281:16:02:01
Block: 67844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093865 RingCT/type: yes/0
Extra: 01997bcc07d9e56992a5a9d614d06ba654ffeea1446ce9e00f8b9ff89c25aca9260211000000024ac5aa02000000000000000000

1 output(s) for total of 365.767801102000 dcy

stealth address amount amount idx
00: f9c0b30af7300a291669d82df3884a166700e3041d55d863c5c8053080c64f4a 365.767801102000 125028 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": 67854, "vin": [ { "gen": { "height": 67844 } } ], "vout": [ { "amount": 365767801102, "target": { "key": "f9c0b30af7300a291669d82df3884a166700e3041d55d863c5c8053080c64f4a" } } ], "extra": [ 1, 153, 123, 204, 7, 217, 229, 105, 146, 165, 169, 214, 20, 208, 107, 166, 84, 255, 238, 161, 68, 108, 233, 224, 15, 139, 159, 248, 156, 37, 172, 169, 38, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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