Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cccccaea6365bd6be7fa645836b21472671de629ce331be24e87a72cf243075

Tx prefix hash: 13b71785c8cf648ffb347e3ea3ff4321d7c14db1ae0f1a06f345a89163e71f82
Tx public key: cf3f4d9ec084f06872c7615d6b899931d0874f0014214f27f19e06c089cc907e
Timestamp: 1706977776 Timestamp [UCT]: 2024-02-03 16:29:36 Age [y:d:h:m:s]: 00:332:23:12:05
Block: 949576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238389 RingCT/type: yes/0
Extra: 01cf3f4d9ec084f06872c7615d6b899931d0874f0014214f27f19e06c089cc907e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e813377924b81f020da0f5b4cae65cecc62f7b2b9c26024eed310e6b144afe60 0.600000000000 1408106 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": 949586, "vin": [ { "gen": { "height": 949576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e813377924b81f020da0f5b4cae65cecc62f7b2b9c26024eed310e6b144afe60" } } ], "extra": [ 1, 207, 63, 77, 158, 192, 132, 240, 104, 114, 199, 97, 93, 107, 137, 153, 49, 208, 135, 79, 0, 20, 33, 79, 39, 241, 158, 6, 192, 137, 204, 144, 126, 2, 17, 0, 0, 0, 2, 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