Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df07d358513981bf56a6ddbb40c2b15bf7dc3252e23c52d00f1e043642560d19

Tx prefix hash: c1cc97ce29918fd642b01082463bd3d4e2591679cd4a7d533db264fd15685429
Tx public key: e2f24fbdda94b5e7331b8b09bf82710007fffc1377e4339fe8ab2ef2f0b77e99
Timestamp: 1698935943 Timestamp [UCT]: 2023-11-02 14:39:03 Age [y:d:h:m:s]: 01:152:00:05:44
Block: 883139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369627 RingCT/type: yes/0
Extra: 01e2f24fbdda94b5e7331b8b09bf82710007fffc1377e4339fe8ab2ef2f0b77e9902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.727434497000 dcy

stealth address amount amount idx
00: cfe23d99ba0636583a410078011dc7485c7129ea36e08658281a1f293e14a83f 0.727434497000 1338827 of 0

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": 883149, "vin": [ { "gen": { "height": 883139 } } ], "vout": [ { "amount": 727434497, "target": { "key": "cfe23d99ba0636583a410078011dc7485c7129ea36e08658281a1f293e14a83f" } } ], "extra": [ 1, 226, 242, 79, 189, 218, 148, 181, 231, 51, 27, 139, 9, 191, 130, 113, 0, 7, 255, 252, 19, 119, 228, 51, 159, 232, 171, 46, 242, 240, 183, 126, 153, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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