Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a6be2489111b570cf1387a16495833cf976e83e125a118d7637c242993ebfe3

Tx prefix hash: 6614f7320df5b316a860548d7e5a358adb2589b365d746f3df491615083d3836
Tx public key: e00aea5fdc55da70bd3053c2f4d6ddc3fd7a17def6a8464b1c777440aaf42e4d
Timestamp: 1675214066 Timestamp [UCT]: 2023-02-01 01:14:26 Age [y:d:h:m:s]: 02:076:10:36:26
Block: 687133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 576268 RingCT/type: yes/0
Extra: 01e00aea5fdc55da70bd3053c2f4d6ddc3fd7a17def6a8464b1c777440aaf42e4d0211000000015029cbac000000000000000000

1 output(s) for total of 3.245211906000 dcy

stealth address amount amount idx
00: 3c07b26beadcd559fabdb6af1439405b7b32fa84ad867296c3608efaab6849ef 3.245211906000 1129689 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": 687143, "vin": [ { "gen": { "height": 687133 } } ], "vout": [ { "amount": 3245211906, "target": { "key": "3c07b26beadcd559fabdb6af1439405b7b32fa84ad867296c3608efaab6849ef" } } ], "extra": [ 1, 224, 10, 234, 95, 220, 85, 218, 112, 189, 48, 83, 194, 244, 214, 221, 195, 253, 122, 23, 222, 246, 168, 70, 75, 28, 119, 116, 64, 170, 244, 46, 77, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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