Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c07fc4f5f75b9cce7c39a3762e9b782544751fcce82c9c321edc690fed59e78

Tx prefix hash: 1adce73c4b588c9d1161c5782c3101b5bdebdd05061b81d0e917e0b3929d3f8b
Tx public key: 61b771e577f2a35eea8103312ae92f11b026b42943977a65b0374db62e691f88
Timestamp: 1736773652 Timestamp [UCT]: 2025-01-13 13:07:32 Age [y:d:h:m:s]: 00:065:09:05:34
Block: 1196476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46520 RingCT/type: yes/0
Extra: 0161b771e577f2a35eea8103312ae92f11b026b42943977a65b0374db62e691f88021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7a7c58160bb594d2c777cd60d781adb2e519cdeef2b2ecdeff1ab9c6caa67b0 0.600000000000 1683075 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": 1196486, "vin": [ { "gen": { "height": 1196476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7a7c58160bb594d2c777cd60d781adb2e519cdeef2b2ecdeff1ab9c6caa67b0" } } ], "extra": [ 1, 97, 183, 113, 229, 119, 242, 163, 94, 234, 129, 3, 49, 42, 233, 47, 17, 176, 38, 180, 41, 67, 151, 122, 101, 176, 55, 77, 182, 46, 105, 31, 136, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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