Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 893cc1a7f1f6e824aa2f4caf939870cee151ed5b75a9c9fe758d436a74b54aef

Tx prefix hash: 1cbd55cb6c098a3b14f41df9e871cded5a8253f45340a469c3843bffeb803fd3
Tx public key: 8f3a022f4cc15e1bcce5763e480c05edf08677038a07649980af89a52ddb61a3
Timestamp: 1680102448 Timestamp [UCT]: 2023-03-29 15:07:28 Age [y:d:h:m:s]: 02:222:19:08:38
Block: 727686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678444 RingCT/type: yes/0
Extra: 018f3a022f4cc15e1bcce5763e480c05edf08677038a07649980af89a52ddb61a3021100000004b3164c24000000000000000000

1 output(s) for total of 2.381630816000 dcy

stealth address amount amount idx
00: 4e9f1e127d1b98b79638aa47d996d7b2f04c3e862800a546bf50a1e3749df09a 2.381630816000 1173011 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": 727696, "vin": [ { "gen": { "height": 727686 } } ], "vout": [ { "amount": 2381630816, "target": { "key": "4e9f1e127d1b98b79638aa47d996d7b2f04c3e862800a546bf50a1e3749df09a" } } ], "extra": [ 1, 143, 58, 2, 47, 76, 193, 94, 27, 204, 229, 118, 62, 72, 12, 5, 237, 240, 134, 119, 3, 138, 7, 100, 153, 128, 175, 137, 165, 45, 219, 97, 163, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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