Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c52a16729b513513f6ebb64164bdd3f68f83ebeaae673fc5386331da8711dad

Tx prefix hash: f159a9d1d59baed357ea107208af2e64fef4d169063f0c03573c0cf53a4efe11
Tx public key: 86e390d2abdc944c3bf57acd5c5ab07a48d568c322c7997900d8de61fa4e2e2a
Timestamp: 1699737430 Timestamp [UCT]: 2023-11-11 21:17:10 Age [y:d:h:m:s]: 01:138:15:18:28
Block: 889572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360264 RingCT/type: yes/0
Extra: 0186e390d2abdc944c3bf57acd5c5ab07a48d568c322c7997900d8de61fa4e2e2a02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.692593934000 dcy

stealth address amount amount idx
00: b06538e8c2271e62bf0bd86a4c4d1e011ab641752ea0ad180bdefb9daef728fd 0.692593934000 1345577 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": 889582, "vin": [ { "gen": { "height": 889572 } } ], "vout": [ { "amount": 692593934, "target": { "key": "b06538e8c2271e62bf0bd86a4c4d1e011ab641752ea0ad180bdefb9daef728fd" } } ], "extra": [ 1, 134, 227, 144, 210, 171, 220, 148, 76, 59, 245, 122, 205, 92, 90, 176, 122, 72, 213, 104, 195, 34, 199, 153, 121, 0, 216, 222, 97, 250, 78, 46, 42, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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