Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2be7607ca68b6d58341c1d2d069f2185534117cf9f7479e0f26ba477718508

Tx prefix hash: 0487d12bf11c7116b1a267e154f34ce58b9794f689b74f53084d16003ecbf2f9
Tx public key: af49594a6b66208b020a2d7791dec23e82629adb5a28a5cc2080c4b14c7e178f
Timestamp: 1695511474 Timestamp [UCT]: 2023-09-23 23:24:34 Age [y:d:h:m:s]: 01:244:01:05:37
Block: 854734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435524 RingCT/type: yes/0
Extra: 01af49594a6b66208b020a2d7791dec23e82629adb5a28a5cc2080c4b14c7e178f021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.903465329000 dcy

stealth address amount amount idx
00: d83166dc0dc0bf97a73347fc5d863081821b60e395e14aa0dbd28adcf0433aca 0.903465329000 1308720 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": 854744, "vin": [ { "gen": { "height": 854734 } } ], "vout": [ { "amount": 903465329, "target": { "key": "d83166dc0dc0bf97a73347fc5d863081821b60e395e14aa0dbd28adcf0433aca" } } ], "extra": [ 1, 175, 73, 89, 74, 107, 102, 32, 139, 2, 10, 45, 119, 145, 222, 194, 62, 130, 98, 154, 219, 90, 40, 165, 204, 32, 128, 196, 177, 76, 126, 23, 143, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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