Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbb2dfc6804b1986dfcdedaf42245150fd94c251cb7ffa729b32b6c7a60382c9

Tx prefix hash: ededbad6f96ae270c8d8c9813e4e9cc903590a261c0a17bbb814aeb7410ab6c2
Tx public key: 42a82e2e16debe76e72e7c73286aa75da27e9465aee843b6d3111877fb3d77d0
Timestamp: 1574737749 Timestamp [UCT]: 2019-11-26 03:09:09 Age [y:d:h:m:s]: 04:346:16:45:47
Block: 17611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129699 RingCT/type: yes/0
Extra: 0142a82e2e16debe76e72e7c73286aa75da27e9465aee843b6d3111877fb3d77d0021100000001f95225a5000000000000000000

1 output(s) for total of 536.608996705000 dcy

stealth address amount amount idx
00: ee275cb9e917ea77ef4c4f76c8176a097db66682848205d302b4bfe6502d53f9 536.608996705000 25837 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": 17621, "vin": [ { "gen": { "height": 17611 } } ], "vout": [ { "amount": 536608996705, "target": { "key": "ee275cb9e917ea77ef4c4f76c8176a097db66682848205d302b4bfe6502d53f9" } } ], "extra": [ 1, 66, 168, 46, 46, 22, 222, 190, 118, 231, 46, 124, 115, 40, 106, 167, 93, 162, 126, 148, 101, 174, 232, 67, 182, 211, 17, 24, 119, 251, 61, 119, 208, 2, 17, 0, 0, 0, 1, 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