Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0fb92a86033cf375252f47d059f541fe8bd42fbfbb1f5db41a16170b1cdf2f6

Tx prefix hash: 4d3e65664f41fbdd471232f3988c4f4ba31e317294b2a4ca004120d78672d2fc
Tx public key: c16525aa8fd0cb8c4c619b111ef10fdacae89ad245a3cada3ad368d6a778e081
Timestamp: 1705853654 Timestamp [UCT]: 2024-01-21 16:14:14 Age [y:d:h:m:s]: 01:151:02:51:58
Block: 940250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368988 RingCT/type: yes/0
Extra: 01c16525aa8fd0cb8c4c619b111ef10fdacae89ad245a3cada3ad368d6a778e0810211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36aadfdd25b2f491f436f15e122458de66170a5733732e1567699002cfd37e3d 0.600000000000 1398384 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": 940260, "vin": [ { "gen": { "height": 940250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36aadfdd25b2f491f436f15e122458de66170a5733732e1567699002cfd37e3d" } } ], "extra": [ 1, 193, 101, 37, 170, 143, 208, 203, 140, 76, 97, 155, 17, 30, 241, 15, 218, 202, 232, 154, 210, 69, 163, 202, 218, 58, 211, 104, 214, 167, 120, 224, 129, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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