Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 795bd0f906f29742e1c5b330f974474a134d517dd0800b02fd853f4beddb9fe3

Tx prefix hash: 2cf4850f5690b8a2ef92613e2674e80113e97deb808bd8bfe28447e6cc69df42
Tx public key: 888330c7a19d84f36ce35a2ef53e6a4e17b7822cbe415756973d66a08252e301
Timestamp: 1672659569 Timestamp [UCT]: 2023-01-02 11:39:29 Age [y:d:h:m:s]: 02:151:22:30:42
Block: 665946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 630323 RingCT/type: yes/0
Extra: 01888330c7a19d84f36ce35a2ef53e6a4e17b7822cbe415756973d66a08252e30102110000000852542ceb000000000000000000

1 output(s) for total of 3.814559714000 dcy

stealth address amount amount idx
00: bbbee4dbd08b16ea8c525afdc2a622c9160bed30bb596dc0e83ec7ffb55b6bc8 3.814559714000 1107017 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": 665956, "vin": [ { "gen": { "height": 665946 } } ], "vout": [ { "amount": 3814559714, "target": { "key": "bbbee4dbd08b16ea8c525afdc2a622c9160bed30bb596dc0e83ec7ffb55b6bc8" } } ], "extra": [ 1, 136, 131, 48, 199, 161, 157, 132, 243, 108, 227, 90, 46, 245, 62, 106, 78, 23, 183, 130, 44, 190, 65, 87, 86, 151, 61, 102, 160, 130, 82, 227, 1, 2, 17, 0, 0, 0, 8, 82, 84, 44, 235, 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