Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b96946ce4d2875b2fd903ba8e50a0f0060fdb402493df44f473d19c70d3512d

Tx prefix hash: 0941cf9357fd08b039a6c2aa753355a7007faae942f191f574b8d22b595d1342
Tx public key: 888cb998506618721da0a0076f437501c9e364ffbfba29d83f78a56eaabe6832
Timestamp: 1727859484 Timestamp [UCT]: 2024-10-02 08:58:04 Age [y:d:h:m:s]: 00:162:02:08:03
Block: 1122717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115650 RingCT/type: yes/0
Extra: 01888cb998506618721da0a0076f437501c9e364ffbfba29d83f78a56eaabe683202110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4b795f6cef961f0cb95d8fa86bf208b737b506c6ebc4e5b4d9773a5dc183172 0.600000000000 1605222 of 15

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": 1122727, "vin": [ { "gen": { "height": 1122717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4b795f6cef961f0cb95d8fa86bf208b737b506c6ebc4e5b4d9773a5dc183172" } } ], "extra": [ 1, 136, 140, 185, 152, 80, 102, 24, 114, 29, 160, 160, 7, 111, 67, 117, 1, 201, 227, 100, 255, 191, 186, 41, 216, 63, 120, 165, 110, 170, 190, 104, 50, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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