Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f3aeb49095623f28a56de414b8c3e4d656cd5e54390571cf0c3043937a62e93

Tx prefix hash: 16b4321a8308408f81dca05eab1deba288b9544772a236a00eb4249bedaa65de
Tx public key: 83b8e23b377b0f5c598aa3346a0105dff09bf9dc9e1c6a9e5cc4375dd37fe631
Timestamp: 1711264353 Timestamp [UCT]: 2024-03-24 07:12:33 Age [y:d:h:m:s]: 01:021:23:48:50
Block: 985153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276677 RingCT/type: yes/0
Extra: 0183b8e23b377b0f5c598aa3346a0105dff09bf9dc9e1c6a9e5cc4375dd37fe63102110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 532db810a3ef2e44bc3b9f93ac5f168cba748138111c91f73f7a940fbcabae5b 0.600000000000 1445360 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": 985163, "vin": [ { "gen": { "height": 985153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "532db810a3ef2e44bc3b9f93ac5f168cba748138111c91f73f7a940fbcabae5b" } } ], "extra": [ 1, 131, 184, 226, 59, 55, 123, 15, 92, 89, 138, 163, 52, 106, 1, 5, 223, 240, 155, 249, 220, 158, 28, 106, 158, 92, 196, 55, 93, 211, 127, 230, 49, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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