Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c70b82d79459ff3e87b7240b7c951e7cc8a0d8e526b2211c318123f2e323e5

Tx prefix hash: 4bce34af8b49c32e4bf0b0ab4f75e6df14053b7ff8b639011937bd6336104aba
Tx public key: 21eff628775aca097a430b18420492b09e6f4f34e595c25beb52b6aa28ac2476
Timestamp: 1711876567 Timestamp [UCT]: 2024-03-31 09:16:07 Age [y:d:h:m:s]: 01:014:08:27:41
Block: 990228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271205 RingCT/type: yes/0
Extra: 0121eff628775aca097a430b18420492b09e6f4f34e595c25beb52b6aa28ac247602110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 246cc316c5d8e33931e2b27fcb63b829ebf7f37b0b1c24659d85bfdc948bc426 0.600000000000 1450550 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": 990238, "vin": [ { "gen": { "height": 990228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "246cc316c5d8e33931e2b27fcb63b829ebf7f37b0b1c24659d85bfdc948bc426" } } ], "extra": [ 1, 33, 239, 246, 40, 119, 90, 202, 9, 122, 67, 11, 24, 66, 4, 146, 176, 158, 111, 79, 52, 229, 149, 194, 91, 235, 82, 182, 170, 40, 172, 36, 118, 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