Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b4f5b17ed9a941030c752242a6c7d6c4f2a62aeea625c4c9282a77e4e38182

Tx prefix hash: 854408bb692fd231345589845d98d1f61f8ba14ee16ac7b9d0c6b1f3860ee37c
Tx public key: bbce7bc7dc36c37e55f3280398adb2a7ce7b33225432881a78389b168853732c
Timestamp: 1725394699 Timestamp [UCT]: 2024-09-03 20:18:19 Age [y:d:h:m:s]: 00:173:23:55:16
Block: 1102279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124170 RingCT/type: yes/0
Extra: 01bbce7bc7dc36c37e55f3280398adb2a7ce7b33225432881a78389b168853732c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0395175d455ace0f9c5063378c72dfa0855f4f7454c32b7d8a05339557a089e2 0.600000000000 1578654 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": 1102289, "vin": [ { "gen": { "height": 1102279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0395175d455ace0f9c5063378c72dfa0855f4f7454c32b7d8a05339557a089e2" } } ], "extra": [ 1, 187, 206, 123, 199, 220, 54, 195, 126, 85, 243, 40, 3, 152, 173, 178, 167, 206, 123, 51, 34, 84, 50, 136, 26, 120, 56, 155, 22, 136, 83, 115, 44, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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