Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8e27c5a41e52c6c362aa99d427b89a018d09f4ab081cf13abd281166e86841a

Tx prefix hash: 921c0d9ef4968841f135493dec8da69012b41132a1b961b904e491d7bb1a7b99
Tx public key: 3581708bbbcbb4f8390bcc9a1ba0473426d61b99f4ed9f419e7f076c4a387ca6
Timestamp: 1681472984 Timestamp [UCT]: 2023-04-14 11:49:44 Age [y:d:h:m:s]: 01:272:02:46:46
Block: 738386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455984 RingCT/type: yes/0
Extra: 013581708bbbcbb4f8390bcc9a1ba0473426d61b99f4ed9f419e7f076c4a387ca60211000000017e406890000000000000000000

1 output(s) for total of 2.194931057000 dcy

stealth address amount amount idx
00: c8839b7106fd055eb90e4dcae7c74f8ea779760120ba64cf762e6ca27a291b14 2.194931057000 1185067 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": 738396, "vin": [ { "gen": { "height": 738386 } } ], "vout": [ { "amount": 2194931057, "target": { "key": "c8839b7106fd055eb90e4dcae7c74f8ea779760120ba64cf762e6ca27a291b14" } } ], "extra": [ 1, 53, 129, 112, 139, 187, 203, 180, 248, 57, 11, 204, 154, 27, 160, 71, 52, 38, 214, 27, 153, 244, 237, 159, 65, 158, 127, 7, 108, 74, 56, 124, 166, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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