Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f938cc987205e1a131e2ff16f6858c0ffc99d25e7c02330c4c306468391b04d3

Tx prefix hash: 27ff7b006e8180122a47b21ecf160a5ddc6faa7e26b398b65d83f48fa32a4aee
Tx public key: 3039ae2e44d64e39645d51ae331caa04567db0693cad23f0ae43c293b665df56
Timestamp: 1713000336 Timestamp [UCT]: 2024-04-13 09:25:36 Age [y:d:h:m:s]: 00:350:01:46:52
Block: 999516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250282 RingCT/type: yes/0
Extra: 013039ae2e44d64e39645d51ae331caa04567db0693cad23f0ae43c293b665df5602110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f0d463265c2d9c4e7cbbd54a09150c43c3769edfe35ef2b6589a6a7b940a9ef 0.600000000000 1459996 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": 999526, "vin": [ { "gen": { "height": 999516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f0d463265c2d9c4e7cbbd54a09150c43c3769edfe35ef2b6589a6a7b940a9ef" } } ], "extra": [ 1, 48, 57, 174, 46, 68, 214, 78, 57, 100, 93, 81, 174, 51, 28, 170, 4, 86, 125, 176, 105, 60, 173, 35, 240, 174, 67, 194, 147, 182, 101, 223, 86, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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