Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa761d9b0b217ce52441073660a197b56d59e1a52a632e140ec78d40a6dc8b5a

Tx prefix hash: 290958eeeb567501fe00dfa6be9b44f26cb8c4f8ef6632168218b0cee584f8db
Tx public key: 1178a7189165363014d4ec3d927273157b1d21034c6f994a3ea381c02d6d7325
Timestamp: 1722102268 Timestamp [UCT]: 2024-07-27 17:44:28 Age [y:d:h:m:s]: 00:175:23:09:44
Block: 1074984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125854 RingCT/type: yes/0
Extra: 011178a7189165363014d4ec3d927273157b1d21034c6f994a3ea381c02d6d7325021100000016e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee04495234fc61ac3ae695d02334c6687acc8875d24d0b4a7e79bb3e6e67f3b8 0.600000000000 1547503 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": 1074994, "vin": [ { "gen": { "height": 1074984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee04495234fc61ac3ae695d02334c6687acc8875d24d0b4a7e79bb3e6e67f3b8" } } ], "extra": [ 1, 17, 120, 167, 24, 145, 101, 54, 48, 20, 212, 236, 61, 146, 114, 115, 21, 123, 29, 33, 3, 76, 111, 153, 74, 62, 163, 129, 192, 45, 109, 115, 37, 2, 17, 0, 0, 0, 22, 233, 20, 221, 21, 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