Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82cc6ea521fca0d61a468ebd19defb83f5265079f5f0faf29a5af4c5ac9ac030

Tx prefix hash: cc8069f55feaaef712307b3e3476cc2cdb61022e3880043504f7b74fb23cd3ad
Tx public key: 535c6bd1e35a373e85435c77bee8428aa4841ba70f26f00652d3d7b77072f1a4
Timestamp: 1710200628 Timestamp [UCT]: 2024-03-11 23:43:48 Age [y:d:h:m:s]: 01:254:23:47:16
Block: 976325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440955 RingCT/type: yes/0
Extra: 01535c6bd1e35a373e85435c77bee8428aa4841ba70f26f00652d3d7b77072f1a40211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1b1e4899b4d8a1e00f5c85c57e91151b8286e3151bc3022539af99b05c2e36a 0.600000000000 1436318 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": 976335, "vin": [ { "gen": { "height": 976325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1b1e4899b4d8a1e00f5c85c57e91151b8286e3151bc3022539af99b05c2e36a" } } ], "extra": [ 1, 83, 92, 107, 209, 227, 90, 55, 62, 133, 67, 92, 119, 190, 232, 66, 138, 164, 132, 27, 167, 15, 38, 240, 6, 82, 211, 215, 183, 112, 114, 241, 164, 2, 17, 0, 0, 0, 4, 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