Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f13268b6cb261e68aef8cf0f7503c841ed178136e170d55fe951fe12f554a681

Tx prefix hash: f35a23f12e37605a3346dc61cbbdc356ca11b65f35e4e93eea2ea7cc7f594d2e
Tx public key: efd0c273c35d03cbc7444b1f7e37d71c89cc64f862634bbc74963b65da99b20b
Timestamp: 1727784388 Timestamp [UCT]: 2024-10-01 12:06:28 Age [y:d:h:m:s]: 00:114:17:02:56
Block: 1122097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81961 RingCT/type: yes/0
Extra: 01efd0c273c35d03cbc7444b1f7e37d71c89cc64f862634bbc74963b65da99b20b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89ba5d4c8d3e986deaf99c24bf47f239d7480ab395f5569e4e2318e9cee7023c 0.600000000000 1604474 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": 1122107, "vin": [ { "gen": { "height": 1122097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89ba5d4c8d3e986deaf99c24bf47f239d7480ab395f5569e4e2318e9cee7023c" } } ], "extra": [ 1, 239, 208, 194, 115, 195, 93, 3, 203, 199, 68, 75, 31, 126, 55, 215, 28, 137, 204, 100, 248, 98, 99, 75, 188, 116, 150, 59, 101, 218, 153, 178, 11, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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